Install
Your BuildBetter team will give you the current approved install command for the CLI preview. The direct installer uses BuildBetter’s release endpoint and installs bb into ~/.local/bin by default.
If ~/.local/bin is not already on your PATH, add it in your shell profile:
Verify the install:
Homebrew and npm install commands are not customer-ready yet. Use the direct installer only when BuildBetter has enabled CLI access for your workspace.
Sign In
The CLI opens a browser sign-in flow and stores local auth configuration under ~/.bb/config.json.
On Unix systems, new auth writes keep that file private to your user account.
Check your signed-in account:
Sign out:
Install Provider Hooks
Run the hook install command inside the git repository where you use your AI coding provider.
For Codex:
For Claude Code:
The command writes provider hook configuration under the current repository by default. The hook calls BuildBetter quietly at the end of each provider turn and uploads the current agent session when you are signed in.
Use user-global provider config instead of repo-local config:
Global installs include a repo-root guard so the hook only runs for the repository where you installed it. Use the default repo-local config when you want the hook definition checked into or shared with the project.
The default hook command fetches BuildBetter’s remote bootstrap script. If bb is already installed everywhere the provider runs, install a direct local command instead:
Inspect, repair, or remove a managed hook:
Use --claude instead of --codex for Claude Code.
Resume Sessions
From the same repository and branch:
The CLI shows uploaded sessions that match the current repository context. Select one to restore the provider-native session locally and launch the matching provider resume command.
